Changes between Version 34 and Version 35 of Installing Pidgin

Timestamp:

Mar 22, 2008, 3:44:47 PM (16 years ago)

Author:

resiak

Comment:

Move the dep installation instructions up to the section about missing dependencies.

Installing Pidgin

@@ -52 +52 @@
 You're probably missing some dependencies.  The configure script will tell you when you are missing required dependencies.  Remember that if you're using an RPM-based (!RedHat Enterprise Linux, CentOS, SUSE, Mandriva, etc.)  or Debian-based system (Debian, Ubuntu, etc.) that having just a library's package installed is not sufficient--you must also have the -devel (RPM systems) or -dev (Debian-based systems) package for each library installed.  If configure is succeeding, but make fails, this is harder to diagnose and you will probably want to drop by the IRC channel or XMPP conference listed on PidginCommunity to get help.
 
-If you're on a Debian-based distribution, you may find `apt-get build-dep pidgin` useful; this requires that you have a `deb-src` line configured in `/etc/apt/sources.list`.
+=== How do I install the dependencies on Debian or Ubuntu? ===
+You need to install the development headers; these are the -dev packages. A simple `apt-get build-dep pidgin` (or if you're on an older release which doesn't have a `pidgin` package, `apt-get build-dep gaim`) will find and install all of the required header packages for you.
+
+If `apt-get build-dep` fails with a message like
+
+> E: You must put some 'source' URIs in your sources.list
+
+then you need to add `deb-src` lines to your `/etc/apt/sources.list` corresponding to each of the `deb` lines already there.  If editing configuration files scares you, Ubuntu has a "Software Sources" control panel in System -> Administration which has some magic tickyboxes to do this for you.
+
+
+=== How do I install the dependencies on Fedora (or similar)? ===
 
 RPM-based distribution users may find `yum-builddep pidgin-VERSION.src.rpm` useful if a source RPM is available and the distribution uses the yum tools.
@@ -92 +102 @@
 In short, there are a lot of good reasons to ''not'' use Pidgin MTN if one does not wish to develop Pidgin, Pidgin plugins, or a codebase which interacts with Pidgin in some intimate way.  There are, however, only a few reasons ''to'' use Pidgin MTN outside of the above.  Please weigh these things carefully and decide whether you wish to use Pidgin MTN for a good reason which furthers the community, or for selfish reasons which are not entirely important.
 
-=== I am on Debian or Ubuntu; how do I get $DEPENDENCY installed so I can compile Pidgin? ===
-You need to install the development headers; these are the -dev packages. A simple `apt-get build-dep pidgin` (or if you're on an older release which doesn't have a `pidgin` package, `apt-get build-dep gaim`) will find and install all of the required header packages for you.
-
-If `apt-get build-dep` fails with a message like
-
-> E: You must put some 'source' URIs in your sources.list
-
-then you need to add `deb-src` lines to your `/etc/apt/sources.list` corresponding to each of the `deb` lines already there.  If editing configuration files scares you, Ubuntu has a "Software Sources" control panel in System -> Administration which has some magic tickyboxes to do this for you.
 
 === How can I get Pidgin to report idleness based on keyboard and mouse usage? ===